Engine Won.t Idle? Changed Lots

[daveheggie]

Hi,

This problem is driving me mad. the original fault was that the engine occasionally idled at 2000 rpm. Then it started to not idle at all but die. I have replaced the plugs and the 2 coil packs and I have checked for leaks/ holes in all of hoses on the inlet manifold side. All made no difference. I have looked at the OBD and there are no faults! I have just purchased the Idle control valve at much expense and still the problem is there it fails to tick over and has a misfire at low rev. Any ideas much appreciated before I run out of money!!

Edited May 17, 2009 by daveheggie

[mikej]

Is the auto choke working ? have you changed the leads etc , if not wait untill its gone dark open the bonnet with no lights on etc and have someone start the car while you have a good close look for arcing on the leads etc, its worth a go and don't cost nowt unless of course they are shot lol.. :ph34r: Edited May 17, 2009 by mikej

[m9wle]

try changing Relay 30 or it may be marked 27 ..... this solved my problem at arounf

[mikej]

I thought relay 30 was to do with non-starting ? :ph34r:

[frogeye]

Hi Mike,

I had a similar problem with my 2.0l Gal last year. After having changed plugs, coil packs and a couple of cleaning attempts at the idle control valve, suddenly solved the problem by simply unpluging the MAF sensor. I guess it was giving duff readings to the ECU. With it unplugged the ECU drops into some default mode that is a lot closer match to the signals that it should be sending. I bought a replacement MAF of ebay (I think) and swapped them over a couple of weeks later. So far so good!

 

I can't think it is to do with the relays (as I had issues with relay 30 with my non starting 2.3 Zetec Galaxy last summer!)

 

Good luck!

Chris

[mikej]

QUOTE:

Hi Mike,

I had a similar problem with my 2.0l Gal last year. After having changed plugs, coil packs and a couple of cleaning attempts at the idle control valve, suddenly solved the problem by simply unpluging the MAF sensor. I guess it was giving duff readings to the ECU. With it unplugged the ECU drops into some default mode that is a lot closer match to the signals that it should be sending. I bought a replacement MAF of ebay (I think) and swapped them over a couple of weeks later. So far so good!

 

I can't think it is to do with the relays (as I had issues with relay 30 with my non starting 2.3 Zetec Galaxy last summer!)

 

Good luck!

Chris

 

I think you mean Dave, my galaxy is running fine :ph34r: for a change lol....

[daveheggie]

OK so I have changed the MAF sensor and reset the ECU but I STILL have the same problem...

 

Any suggestions,

 

THE OBD now has code P1121

 

 

QUOTE:

Hi Mike,

I had a similar problem with my 2.0l Gal last year. After having changed plugs, coil packs and a couple of cleaning attempts at the idle control valve, suddenly solved the problem by simply unpluging the MAF sensor. I guess it was giving duff readings to the ECU. With it unplugged the ECU drops into some default mode that is a lot closer match to the signals that it should be sending. I bought a replacement MAF of ebay (I think) and swapped them over a couple of weeks later. So far so good!

 

I can't think it is to do with the relays (as I had issues with relay 30 with my non starting 2.3 Zetec Galaxy last summer!)

 

Good luck!

Chris

 

I think you mean Dave, my galaxy is running fine :ph34r: for a change lol....

[seatkid]

OK so I have changed the MAF sensor and reset the ECU but I STILL have the same problem...

 

Any suggestions,

 

THE OBD now has code P1121

 

P1121 - Throttle Position Sensor inconsistent with MAF sensor

 

possible causes are:

 

* Air leak between MAF sensor and throttle body - check the intake tube for leaks and proper fit.

* TP sensor not seated properly

* Faulty TP sensor or wiring

* Faulty MAF sensor or wiring

Edited May 28, 2009 by seatkid